System and method for comparing drug product information

ABSTRACT

A system and method for comparing vast amounts of drug product information at granular levels is provided. This comparison is facilitated by the creation of a unique key that maintains the integrity of the comparison system. The unique key may contain a therapeutic class identifier, a clinical formulation identifier, an additional detail identifier, a package equivalent size identifier, a unit dose identifier, and a package quantity identifier.

FIELD OF INVENTION

The present invention is generally related to supply chain management inthe pharmaceutical industry, and more particularly, to the comparison,storage, management and ordering of pharmaceutical and associatedproduct information.

BACKGROUND OF THE INVENTION

In general, the management and ordering of pharmaceuticals for anorganization, such as a hospital pharmacy department, is an expensiveendeavor. Oftentimes, pharmacy departments have some of the highestexpenses in a hospital. As such, in today's cost sensitive healthenvironment, healthcare organizations are constantly challenging theirpharmacy departments to reduce costs and spending.

While many factors contribute to high administrative costs, onecontributing factor is the number of drugs an organization needs totrack and/or order. In an effort for a health organization to bettercontrol its costs, the organization usually needs to access accuratepricing quotes for drugs offered through multiple manufacturers.However, the same or similar drug may be offered in many differentpackage sizes, routes of administration, strength, dosage forms and thelike. Adding to this complexity, the generic drug market is expanding atan exponential rate with new companies producing generically equivalentproducts. As such, a particular drug may be known by many differentnames such as a trademarked name of a drug or its generic or chemicalname.

Due to these complexities, many healthcare providers utilize supplychain management companies that have created systems which aggregatevast amounts of drug information and provide this information tohealthcare providers. Providers use these various systems to aid withthe management of drug information and supply contracts associated withthese drugs. By utilizing this information, healthcare providers areable to better control costs, increase their negotiating power with drugsuppliers during contract negotiations, increase the accuracy of theirorders, and facilitate quicker payment resolution. However, due todifferences in product naming conventions, manufacturer's productdescriptions, strengths, and dosages and the like amongst the same orsimilar active ingredients of a drug, much of the aggregated data cannotbe easily cross-referenced according to the generic name across variousmanufacturers that produce a drug. For example, oftentimes a drugmanufacturer will sell its trademarked brand of drug without everreferring to the active ingredient or generic name of the drug. As such,it is difficult for a healthcare provider to obtain the best contractpurchase price or to reconcile inventory projections and usage.

Thus, a longtime need exists for a system and method that captures andorganizes drug product information at the generic level so that acomparison can be made across various manufacturers.

SUMMARY OF THE INVENTION

The present invention includes systems and methods for comparing andstoring drug product information. An exemplary system for drug productinformation comparison comprises one or more data feeds, a processingengine, a database, and a reporting engine. Drug product information isgleaned from various data feeds comprising data describing drugs andtheir characteristics, manufacturers and wholesalers, contractinformation, membership information and/or the like. The processingengine parses the incoming data feeds and assembles a unique key so thatthe data feed information can be inserted into the database whilemaintaining data integrity. The unique key may contain a therapeuticclass identifier, a clinical formulation identifier, an additionaldetail identifier, a package equivalent size identifier, a unit doseidentifier, and a package quantity identifier. The reporting engineenables access by a user such that the user can run various reports.

An exemplary method includes the steps of parsing incoming data feed(s)of drug product information, assembling unique keys based on suchinformation, storing unique keys and drug product information in adatabase, receiving report criteria, retrieving report data from adatabase based on the criteria and using the unique key, and outputtingthe report data. The reporting engine may contain pre-determined reportsto facilitate quick comparisons and expedited reporting. Report data maybe output first at a summary level according to the most often usedcriteria, along with the ability to retrieve more detailed data byselecting elements on the summary report. In that regard, the presentinvention enables vast amounts of drug product information to becompared and cross-referenced at generic level.

DESCRIPTION OF THE FIGURES

These and other features, aspects, and advantages of the invention maybest be understood by reference to the following description taken inconjunction with the accompanying drawings in which like numeralsrepresent like elements:

FIG. 1 shows an exemplary drug product information comparison system inaccordance with an exemplary embodiment of the present invention; and,

FIG. 2 shows a flow chart of an exemplary method for comparing drugproduct information in accordance with an exemplary embodiment of thepresent invention.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

The present invention facilitates the storage, comparison andcross-referencing of drug product information at a generic level. Theinvention includes a system and method for comparing drug productinformation, using small fragments of data, without the need to knowmanufacturer specific information, the NDC (National Drug Code)designation, or trade name for each drug. Drug product informationincludes, for example, any information describing drugs and theiringredients and characteristics, manufacturers and wholesalers, contractinformation, membership information or any information typicallyutilized in the supply chain management of the pharmaceutical andhealthcare industry. For example, many similar drugs contain the sameactive ingredients, but have different attributes such as, for example,inactive ingredients, dosages, strengths, route of administration, andthe like. In order to facilitate cost and spending reductions, theinvention enables health care organizations to compare the various drugsat a granular level.

Based on such a comparison, purchase history, contract compliance,request for quotations and/or various other management functions may beperformed. For example, suitable drug substitutes (e.g., generic vs.trademarked drug) or identification of a competitive manufacturer may befound. For example, drug manufacturer A may sell a drug under atrademark in pill form containing 20 MG of active ingredient per pill inbottles of 50 pills. Drug manufacturer B may sell the same drug under adifferent trademark containing 20 MG of active ingredient per pill butin bottles of 100 pills. Drug manufacturer A may price the drug so thatthe cost per pill is more than drug manufacturer B's 20 MG pill. Thepresent invention enables the comparison of the two drugs at a levelgranular enough so that a healthcare provider could identify the lowercost per pill, and employ cost saving measures to use the less expensivemanufacturer B product.

Moreover, a healthcare organization or a manufacturer may use thesystems and methods of the present invention in contract bidding. Drugproduct information may be summed by a number of characteristicsvaluable in the contract bidding process. For example, a bidder maygenerate reports that reveal manufacturer market share according to theproduct(s) contained in the request for quotations (RFQ). The bidder mayanalyze whether a particular contract is suitable should the contract beawarded to the bidder. The healthcare organization who originated theRFQ may use the systems and methods of the present invention to groupand compare the responses. For example, the responses may be groupedaccording to generic name, route of administration, dosage form,strength, package type, package size, and/or package quantity regardlessof the manufacturer. The response may be further sorted according to bidcost (e.g., lowest to highest bid price). In doing so, a healthcareorganization can quickly organize bid responses and select theappropriate bid for its needs.

Because the data that describes the various attributes of the variousdrug products is maintained by separate entities and describeddifferently within each entity, the invention facilitates maintainingintegrity across the disparate data sources. The integrity isfacilitated by the creation of a unique key, wherein the unique key, inone embodiment, is dependent partially on the data sources, and the keycontains an identifier independent of any one particular data source.Because this integrity is maintained, drug product informationcomparisons can be made with increased specificity and in a definitivemanner. For example, if a particular healthcare organization seeksinformation for dye free pediatric liquid medications, reports aregenerated that do not contain medications that incorporate a dye. Thus,as will become apparent from the following descriptions, the systems andmethods of the invention facilitate comparing vast amounts of drugproduct information based on a unique key that enables cross-referencingacross such drug product information.

For the sake of brevity, conventional data networking, applicationdevelopment and other functional aspects of the systems (and componentsof the individual operating components of the systems) may not bedescribed in detail herein. Furthermore, the connecting lines shown inthe various figures contained herein are intended to represent exemplaryfunctional relationships and/or physical couplings between the variouselements. It should be noted that many alternative or additionalfunctional relationships or physical connections may be present in apractical system.

The invention may be described herein in terms of functional blockcomponents, optional selections and various processing steps. It shouldbe appreciated that such functional blocks may be realized by any numberof hardware and/or software components configured to perform thespecified functions. For example, the invention may employ variousintegrated circuit components, e.g., memory elements, processingelements, logic elements, look-up tables, and the like, which may carryout a variety of functions under the control of one or moremicroprocessors or other control devices.

Similarly, the software elements of the invention may be implementedwith any programming, scripting language or web service protocols suchas C, C++, Macromedia Cold Fusion, Microsoft Active Server Pages, Java,COBOL, assembler, PERL, Visual Basic, SQL Stored Procedures, extensiblemarkup language (XML), with the various algorithms being implementedwith any combination of data structures, objects, processes, routines orother programming elements. Further, it should be noted that theinvention may employ any number of conventional techniques for datatransmission, signaling, data processing, network control, and the like,e.g., TCP/IP, IPX, Appletalk, IP-v6, NetBIOS, OSI or any number ofexisting or future protocols. For additional information oncommunication systems, network programming, web services, and security,refer to Gilber Held, “Understanding Data Communications,” (1996); DilipNaik, “Internet Standards and Protocols,” (1998); and Java 2 Complete,various authors (Sybex 1999); the Object Management Group website athttp://.omg.org; the Sun Microsystems JAVA web site athttp://www.sunjava.com; the Universal Description, Discovery, andIntegration Organization at http://www.uddi.org; and “Cryptography &Network Security: Principles & Practice” by William Stalling, publishedby Prentice Hall; all of which are incorporated by reference.

FIG. 1 illustrates, in block format, an exemplary drug productinformation comparison system 100 of the invention. In one embodiment,drug product information comparison system comprises one or more datafeeds 110, a processing engine 120, a database 130, and a reportingengine 140. The system components communicate over one or more networks150, using any of the protocols described herein or are suited to theparticular component and communication.

Data feed 110 may include any collection of data or information suitablefor processing by the system 100. Data feed 110 may be internal orexternal to the system 100 and be provided in various formats such as,for example, ASCII or XML. Data feed 110 will contain recordsrepresenting a collection of fields that may describe any number ofaspects of the information to be included in the system 100. Each recordmay have a unique attribute, such as a number, field, or set of fields)which may uniquely identify the record within the particular data feed.Multiple data feeds may be utilized to gather information for a varietyof sources. In its exemplary embodiments, the information containedwithin the data feeds describe various drug product informationattributes, for example, drug composition, wholesaler information,national drug code information (e.g., from the National Drug CodeDirectory provided by the U.S. Food and Drug Administration), contractinformation, and/or membership information (e.g., whether a particulardrug belongs in a particular health plan, or whether a particularorganization belongs in a membership-only purchasing network).

Processing engine 120 includes any hardware and/or software suitablyconfigured to parse incoming data feed(s) 110 and to assemble a uniquekey enabling comparison and cross-referencing of drug productinformation at a generic level. In general, processing engine 120 isimplemented as a combination of databases, servers, and applicationsoftware that are configured so that the data feed(s) 110 pass throughprocessing engine 120 to be parsed, and so that drug product informationand the unique key can be input into database 130. Operation ofprocessing engines to running parsing, assembly, and database managementfunctions is known and will not be described in detail. In variousembodiments, it should be appreciated that, although not shown ordescribed, additional connections, links and/or adapter interfaces mayoccur between components of the system such as connections to a wirelessbase station, web translation server, router, and/or a coordinatorsystem to drive routing within the system. In this manner, processingengine 120 may include multiple networks capable of communicationbetween networks and other components of the system.

Database 130 may be any type of database, such as relational,hierarchical, object-oriented, and/or the like. Common database productsthat may be used to implement the databases include DB2 by IBM (WhitePlains, N.Y.), any of the database products available from OracleCorporation (Redwood Shores, Calif.), Microsoft Access by MicrosoftCorporation (Redmond, Wash.), or any other database product. Database130 may be organized in any suitable manner, including as data tables orlookup tables. Association of certain data may be accomplished throughany data association technique known and practiced in the art. Forexample, the association may be accomplished either manually orautomatically. Automatic association techniques may include, forexample, a database search, a database merge, GREP, AGREP, SQL, and/orthe like. The association step may be accomplished by a database mergefunction, for example, using a “key field” in each of the manufacturerand retailer data tables. A “key field” partitions the databaseaccording to the high-level class of objects defined by the key field.For example, a certain class may be designated as a key field in boththe first data table and the second data table, and the two data tablesmay then be merged on the basis of the class data in the key field. Inthis embodiment, the data corresponding to the key field in each of themerged data tables is preferably the same. However, data tables havingsimilar, though not identical, data in the key fields may also be mergedby using AGREP, for example.

The data set annotation may also be used for other types of statusinformation as well as various other purposes. For example, the data setannotation may include security information establishing access levels.The access levels may, for example, be configured to permit only certainindividuals, levels of employees, companies, or other entities to accessdata sets, or to permit access to specific data sets based on thetransaction, health care institution, user or the like. Furthermore, thesecurity information may restrict/permit only certain actions such asaccessing, modifying, and/or deleting data sets. In one example, thedata set annotation indicates that only the data set owner or the userare permitted to delete a data set, various identified users may bepermitted to access the data set for reading, and others are altogetherexcluded from accessing the data set. However, other access restrictionparameters may also be used allowing various entities to access a dataset with various permission levels as appropriate.

One skilled in the art will also appreciate that, for security reasons,any databases, systems, devices, servers or other components of thesystem may consist of any combination thereof at a single location or atmultiple locations, wherein each database or system includes any ofvarious suitable security features, such as firewalls, access codes,encryption, decryption, compression, decompression, and/or the like.

A reporting engine 140 includes any hardware and/or software suitablyconfigured to accept input through an interface, query the database 130,and retrieve and output results of the query from database 130. Ingeneral, reporting engine 140 is implemented as a combination ofdatabases, servers, and application software that are configured so thata user (defined as any human entity or electronic means such as asoftware or hardware agent) may access drug product information througha variety of interface and/or networks. Various reporting engines andtheir operational characteristics are known and will not be described indetail. As such, it should be appreciated that, although not shown ordescribed, additional connections, links, hardware, software, databases,and/or interfaces and the like may be used to produce various reportswith respect to the system. In yet other embodiments, the reportingengine 140 is configured to provide audit trails sufficient to meet anyregulatory or auditing requirements with respect to the hardware,software, or data employed in the system.

In accordance with the present invention and with reference to FIG. 2,an exemplary method includes, in general, parsing incoming data feed(s)of drug product information (step 200), assembling unique keys based onsuch information (step 205), storing the unique keys in a database (step210), receiving report criteria (step 215), retrieving report data froma database based on the criteria and using a unique key (step 220), andoutputting the report data (step 225).

In various embodiments, parsing incoming data feed(s) (step 200)includes selecting those parts of the data feed which identify aparticular attribute unique to the feed and creating an identifier. Forexample, a data feed may include the description and therapeutic classof a number of drug products. In this feed, each product may have beenassigned a unique element (e.g., a number, field, or set of fields) bythe originator of the data feed. The parsing function identifies theunique attribute (which would identify a record in the data feed) andnotes it for later assembly. Identification of the unique attribute in adata feed may be pre-determined (e.g., one knows that the first fourcharacters of a line in a data feed represent the unique attribute) orthe parsing function may employ artificial intelligence designed toidentify the unique attribute for each data feed. In variousembodiments, some of the parsing functions may be performed by humanintervention through a user interface. For example, human interventionmay be needed to provide (i.e., insert into the data feed) a uniqueattribute for the particular data feed. Although an example has beenprovided describing a unique attribute in the data feed, there is norequirement that a particular attribute in any data feed be unique;rather, the records associated with data feed should simply beidentified with certainty in the parsing process. Once the uniqueattribute is parsed, this attribute is considered the data feedidentifier for the particular data feed.

After the parsing process, assembling unique keys based on data feedinformation (step 205) comprises assembling the parsed data feedidentifiers into one key that uniquely identifies each drug product tobe contained in database 130. In an exemplary embodiment, the data feedidentifiers are concatenated together with an identifier not dependenton any data feed. However, any technique (e.g., data translation, use ofcryptographic methods, etc.) that assembles identifiers into a uniquekey may be suitable.

In various embodiments, the unique key comprises a therapeutic classidentifier; a clinical formulation identifier; an additional detailidentifier; a billing unit identifier; a unit dose identifier; and apackage size equivalent identifier. In exemplary embodiments, the lengthof the unique key is 25 characters.

In various embodiments, the therapeutic class identifier represents thelist of ingredients in a particular drug formulation. The therapeuticclass identifier identifies a unique combination of active ingredientsin a particular drug product irrespective of the manufacturer, packagesize, dosage form, route of administration, or strength. The number maybe of any length; however, in an exemplary embodiment, the length is sixcharacters. For example, a therapeutic class identifier, 000222, mayidentify the unique set of active ingredients: guaifenesin,dextromethorphan hydrobromide, and pseudoephedrine. Another therapeuticclass identifier, 000223, may identify the unique set of activeingredients: guaifenesin, dextromethorphan hydrobromide, andacetaminophen. In one embodiment, the therapeutic identifier does notcontain inactive ingredients.

In various embodiments, a clinical formulation identifier represents aunique combination of the ingredient(s), the route of administration,the dosage form, and/or the strength for a generic drug formulation. Indoing so, the clinical formulation identifier aggregates drug productsthat share the same or similar characteristics, but are marketed bymultiple manufacturers. Unlike the therapeutic class identifier whichonly identifies active ingredients, the clinical formulation identifiercomprises an identifier that represents the full list of ingredients inthe particular drug formulation. The identifier also comprises the routeof administration which describes the method by which a drug isadministered (e.g., oral, injection, topical, etc.). The dosage form isrepresented by a code which describes the form of the genericformulation of the drug such as tablet, capsule, or the like. Thestrength is represented by a code which describes the drug's potency.

To facilitate comparison, each combination of ingredients, route ofadministration, dosage, and strength is uniquely identified. Forexample, a generic drug formulation containing fluoxetine may differonly in strength. A drug product containing fluoxetine, taken orally, inthe form of a capsule, and in 10 MG strength may be assigned a clinicalformulation identifier of 046213. A drug product containing fluoxetine,taken orally, in the form of a capsule, and in 20 MG strength may beassigned a clinical formulation identifier of 046214. The length of theclinical formulation identifier may be of any length; however, in anexemplary embodiment, the length is six characters.

In various embodiments, the additional detail identifier representsunique details about a particular drug product not captured with theother identifiers. If a particular drug product does not possess anyadditional details, this identifier is set to a null value or character.For example, a drug product may be described as sterile. In this case,the additional detail identifier may be set to 0041. Another product maybe described as “sulfite free” for which the additional detailidentifier is set to 0042. The value of the additional detail identifierwill be unique across the complete set of additional details describedin the system. The length of the additional detail identifier may be ofany length; however, in an exemplary embodiment, the length is fourcharacters.

In various embodiments, the package size equivalent identifierrepresents the package size ranges of a particular drug product. Minorvariations in the volume of packaging are used across differentmanufacturers. For example, one manufacturer may label and fill aproduct with 31 mL of liquid, while another manufacturer may label andfill their product with 28 mL of liquid. In both cases, the activeingredients, and therefore the therapeutic benefits, are the same inboth packages. However, to facilitate comparison of drug productinformation across manufacturers, the minor variations in packaging sizemust be normalized. As such, the actual package size is examined andassociated with a standard package size equivalent. Table 1 shows anon-limiting sample of standard package sizes assigned to standardpackage size equivalents.

Package Size Range Package Size Equivalent Description 14.00 to 16.0015.00 15 mL = ½ fl. oz. 26.250 to 31.00  30.00 30 mL = 1 fl. oz. 3500 to4000 4000  4 gm = ⅛ oz

In some cases, the package size range will not be able to be assigned apackage size equivalent. In such cases, the package size equivalentidentifier is given a default value or assigned the same value as thepackage size. The length of the package size equivalent identifier maybe any length; however, in an exemplary embodiment, the length is fourcharacters.

In various embodiments, the unit dose identifier represents whether adrug product contains separate unit doses or unit dose packaging, forexample, blister packs. The unit dose identifier enables theidentification of the drug from the time the drug leaves themanufacturer to the time a patient uses the drug. For example, amanufacturer may provide 100 tablets of a drug with each tablet in anindividually sealed and fully labeled blisterpack. The blisterpack labelmay contain various information describing the drug such as, forexample, trade name, generic name, strength, NDC designation, lotnumber, expiration date, manufacturer name and/or other information(e.g., bar coding). However, the unit dose identifier represents thateach tablet is considered a unit dose. Without the identifier, the factthat unit doses exist would be lost. Consequently, the unit doseidentifier is not applicable in the case of injectable drug products,suppositories, bulk containers or powder-based. As such, the unit doseidentifier is assigned a null or default value. The length of the unitdose identifier may be any length; however, in an exemplary embodiment,the length is two characters. For example, the unit dose identifier fora drug product containing unit doses would be set to 01.

In various embodiments, the pack quantity identifier represents thenumber of units within a particular package. For example, one injectabledose of a drug may be packaged in a 2 mL vial. However, the manufacturermay package multiple vials in one box. So that the proper comparisonsbetween all the attributes of the particular drug can be made, thenumber of vials in the package must be accounted for. As such, thepackage quantity identifier is assigned a unique number for the numberof units in the package. For example, if a box contains 5 units, thepackage identifier is assigned 001; a box containing 25 units may beassigned a package quantity identifier 005. The identifier is uniqueamong packages sizes so that once an identifier is assigned to a packagequantity, this assignment remains unique. The length of the packquantity identifier may be any length; however, in an exemplaryembodiment, the length is three characters.

After assembly, storing the unique keys in a database (step 210)comprises inputting the unique keys and associated drug productinformation into the database for storage and retrieval by the reportingengine. Various database schemas may be utilized to efficiently storedrug product information; however, in one embodiment, all drug productinformation is related through the unique key. In an exemplaryembodiment, not all information contained in the data feed is savedafter parsing. The parsing process may also include the deletion ofextraneous data from the data feed before inclusion in the database.

In its embodiments, receiving report criteria (step 215) comprises auser inputting various report criteria through an interface, upon whichthe interface submits the criteria to the database. Access may beconducted directly through a human operator, or through automatedsoftware programs. As such, a user includes any and all agents that mayaccess the reporting engine. In exemplary embodiments, access isachieved by a human operator through a web page.

Upon access, the user is presented with various reporting criteria toselect from. For example, reporting criteria includes any fieldcontained in the database. However, in an exemplary embodiment, mostoften used parameters may be presented to a user such as manufacturername, drug name (e.g., generic name or trademark name), price ranges,national drug code number and the like, with other parameters selectableupon further browsing of the interface. The user may submit any numberof reporting criteria through the interface. After selection of thereporting criteria, the user submits the criteria to the database.

In its embodiments, retrieving report data from a database based on thecriteria and using a unique key (step 220) comprises the reportingengine creating an appropriate query and transmitting the query to thedatabase. Any query language configured to the particular databasesystem employed is suitable. In exemplary embodiments, the querycomprises the unique key so that comparison and cross-referencingintegrity is maintained. Furthermore, various reports may be“pre-determined” such that queries may be assembled quickly without theneed to repeat the selection of all desired criteria upon each access tothe system.

In its embodiments, outputting the report data (step 225) comprisestransmitting the data retrieved from the database to the reportingengine and finally to the user. Data may be displayed in any matter;however, in exemplary embodiments, summary data is displayed by mostoften used criteria such as manufacturer, drug product, or national drugcode number. The user is able to select summary data elements (i.e.,“drill down”) to retrieve more specific and detailed data related to theelement selected. In various embodiments, reports may be printed, savedto storage media, or otherwise manipulated for final consumption. Anexemplary report includes grouping drug product information according togeneric name, route of administration, dosage form, strength, packagetype, package size, and/or package quantity regardless of themanufacturer, trade name, or NDC designation. Another exemplary reportincludes grouping drug product information according to generic name,route of administration, dosage form, strength, and/or package type. Yetanother exemplary report includes grouping drug product informationaccording to NDC designation by manufacturer use, total use, and/ormarket share. Yet another exemplary report is grouping drug productinformation according to the price bid by a particular manufacturer in acontract bidding process.

As used herein, the term “network” shall include any electroniccommunications means which incorporates both hardware and softwarecomponents of such. Communication among the systems may be accomplishedthrough any suitable communication channels, such as, for example, atelephone network, an extranet, an intranet, Internet, point ofinteraction device (point of sale device, personal digital assistant(e.g., Palm Pilot®, Blackberry®), cellular phone, kiosk, etc.), onlinecommunications, satellite communications, off-line communications,wireless communications, transponder communications, local area network(LAN), wide area network (WAN), networked or linked devices, keyboard,mouse and/or any suitable communication or data input modality.Moreover, the system may also be implemented using TCP/IP, IPX,Appletalk, IP-6, NetBIOS, OSI or any number of existing or futureprotocols. If the network is in the nature of a public network, such asthe Internet, it may be advantageous to presume the network to beinsecure and open to eavesdroppers. Specific information related to theprotocols, standards, and application software utilized in connectionwith the Internet is generally known to those skilled in the art and, assuch, need not be detailed herein. See, for example, Dilip Naik,Internet Standards and Protocols (1998); Java 2 Complete, variousauthors, (Sybex 1999); Deborah Ray and Eric Ray, Mastering HTML 4.0(1997); and Loshin, TCP/IP Clearly Explained (1997) and David Gourleyand Brian Totty, HTTP, The Definitive Guide (2002), the contents ofwhich are hereby incorporated by reference.

The various system components may be independently, separately orcollectively suitably coupled to network 150 via data links whichincludes, for example, a connection to an Internet Service Provider(ISP) over the local loop as is typically used in connection withstandard modem communication, cable modem, Dish networks, ISDN, DigitalSubscriber Line (DSL), or various wireless communication methods, see,e.g., Gilbert Held, Understanding Data Communications (1996), which ishereby incorporated by reference. Moreover, the system contemplates theuse, sale or distribution of any goods, services or information over anynetwork having similar functionality described herein.

As used herein, “transmit” may include sending electronic data from onesystem component to another over a network connection. Additionally, asused herein, “data” or “information” may include encompassinginformation such as commands, queries, files, data for storage, and thelike in digital or any other form.

In various embodiments, user interface may include a web-compliantdevices suitably capable of processing web pages and multimediainformation (i.e., text, graphics, video and/or audio), and may includeweb-client software, an audio processor, a visual display, and/or anaudio transducers. Web-compliant devices may be of a type capable ofestablishing a packet communication link via the Internet using a commonprotocol, e.g., Hyper-Text Transfer Protocol (HTTP), the operation ofwhich is beyond the scope of this invention and will not be described indetail.

The various system components discussed herein may include one or moreof the following: a host server or other computing systems including aprocessor for processing digital data; a memory coupled to the processorfor storing digital data; an input digitizer coupled to the processorfor inputting digital data; an application program stored in the memoryand accessible by the processor for directing processing of digital databy the processor; a display device coupled to the processor and memoryfor displaying information derived from digital data processed by theprocessor; and a plurality of databases. Various databases used hereinmay include: client data; health care institution data; drug productdata; safety data; manufacturer data and/or like data useful in theoperation of the system. As those skilled in the art will appreciate,devices may include an operating system (e.g., Windows NT, 95/98/2000,OS2, UNIX, Linux, Solaris, MacOS, etc.) as well as various conventionalsupport software and drivers typically associated with computers. Thecomputer may include any suitable personal computer, network computer,workstation, minicomputer, mainframe or the like. User computer can bein a home or business environment with access to a network. In anexemplary embodiment, access is through a network or the Internetthrough a commercially-available web-browser software package.

The system contemplates uses in association with web services, utilitycomputing, pervasive and individualized computing, security and identitysolutions, autonomic computing, commodity computing, mobility andwireless solutions, open source, biometrics, grid computing and/or meshcomputing.

The computing unit of the web client may be further equipped with anInternet browser connected to the Internet or an intranet using standarddial-up, cable, DSL or any other Internet protocol known in the art.Transactions originating at a web client may pass through a firewall inorder to prevent unauthorized access from users of other networks.

Firewall may include any hardware and/or software suitably configured toprotect components and/or enterprise computing resources from users ofother networks. Further, a firewall may be configured to limit orrestrict access to various systems and components behind the firewallfor web clients connecting through a web server. Firewall may reside invarying configurations including Stateful Inspection, Proxy based andPacket Filtering among others. Firewall may be integrated within a webserver or any other components or may further reside as a separateentity.

The components discussed herein may provide a suitable website or otherInternet-based graphical user interface which is accessible by users. Inone embodiment, the Microsoft Internet Information Server (IIS),Microsoft Transaction Server (MTS), and Microsoft SQL Server, are usedin conjunction with the Microsoft operating system, Microsoft NT webserver software, a Microsoft SQL Server database system, and a MicrosoftCommerce Server. Additionally, components such as Access or MicrosoftSQL Server, Oracle, Sybase, Informix MySQL, Interbase, etc., may be usedto provide an Active Data Object (ADO) compliant database managementsystem.

Any of the communications, inputs, storage, databases or displaysdiscussed herein may be facilitated through a website having web pages.The term “web page” as it is used herein is not meant to limit the typeof documents and applications that might be used to interact with theuser. For example, a typical website might include, in addition tostandard HTML documents, various forms, Java applets, JavaScript, activeserver pages (ASP), common gateway interface scripts (CGI), extensiblemarkup language (XML), dynamic HTML, cascading style sheets (CSS),helper applications, plug-ins, and the like. A server may include a webservice that receives a request from a web server, the request includinga URL and an IP address. The web server retrieves the appropriate webpages and sends the data or applications for the web pages to the IPaddress. Web services are applications that are capable of interactingwith other applications over a communications means, such as theinternet. Web services are typically based on standards or protocolssuch as XML, SOAP, WSDL and UDDI. Web services methods are well known inthe art, and are covered in many standard texts. See, e.g., Alex Nghiem,IT Web Services: A Roadmap for the Enterprise (2003), herebyincorporated by reference.

Practitioners will also appreciate that there are a number of methodsfor displaying data within a browser-based document. Data may berepresented as standard text or within a fixed list, scrollable list,drop-down list, editable text field, fixed text field, pop-up window,and the like. Likewise, there are a number of methods available formodifying data in a web page such as, for example, free text entry usinga keyboard, selection of menu items, check boxes, option boxes, and thelike.

As will be appreciated by one of ordinary skill in the art, the systemmay be embodied as a customization of an existing system, an add-onproduct, upgraded software, a stand alone system, a distributed system,a method, a data processing system, a device for data processing, and/ora computer program product. Accordingly, the system may take the form ofan entirely software embodiment, an entirely hardware embodiment, or anembodiment combining aspects of both software and hardware. Furthermore,the system may take the form of a computer program product on acomputer-readable storage medium having computer-readable program codemeans embodied in the storage medium. Any suitable computer-readablestorage medium may be utilized, including hard disks, CD-ROM, opticalstorage devices, magnetic storage devices, and/or the like.

These computer program instructions may be loaded onto a general purposecomputer, special purpose computer, or other programmable dataprocessing apparatus to produce a machine, such that the instructionsthat execute on the computer or other programmable data processingapparatus create means for implementing the functions specified in theflowchart block or blocks. These computer program instructions may alsobe stored in a computer-readable memory that can direct a computer orother programmable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including instruction meanswhich implement the function specified in the flowchart block or blocks.The computer program instructions may also be loaded onto a computer orother programmable data processing apparatus to cause a series ofoperational steps to be performed on the computer or other programmableapparatus to produce a computer-implemented process such that theinstructions which execute on the computer or other programmableapparatus provide steps for implementing the functions specified in theflowchart block or blocks.

Accordingly, functional blocks of the block diagrams and flowchartillustrations support combinations of means for performing the specifiedfunctions, combinations of steps for performing the specified functions,and program instruction means for performing the specified functions. Itwill also be understood that each functional block of the block diagramsand flowchart illustrations, and combinations of functional blocks inthe block diagrams and flowchart illustrations, can be implemented byeither special purpose hardware-based computer systems which perform thespecified functions or steps, or suitable combinations of specialpurpose hardware and computer instructions. Further, illustrations ofthe process flows and the descriptions thereof may make reference touser windows, web pages, websites, web forms, prompts, etc.Practitioners will appreciate that the illustrated steps describedherein may comprise in any number of configurations including the use ofwindows, web pages, web forms, popup windows, prompts and the like. Itshould be further appreciated that the multiple steps as illustrated anddescribed may be combined into single web pages and/or windows but havebeen expanded for the sake of simplicity. In other cases, stepsillustrated and described as single process steps may be separated intomultiple web pages and/or windows but have been combined for simplicity.

Finally, it should be understood that various principles of theinvention have been described in illustrative embodiments. However, manycombinations and modifications of the above-described components, usedin the practice of the invention, in addition to those not specificallydescribed, may be varied and particularly adapted to specificenvironments and operating requirements without departing from thoseprinciples. Other variations and modifications of the present inventionwill be apparent to those of ordinary skill in the art, and it is theintent that such variations and modifications be covered.

1. A system for drug product information comparison comprising: a datafeed; a processing engine configured to receive the data feed, parse thedata feed and assemble a unique key, wherein the unique key comprises apackage quantity identifier and at least one of a therapeutic classidentifier, a clinical formulation identifier, an additional detailidentifier, a package size equivalent identifier, and a unit doseidentifier; a database configured to store information from the datafeed according to the unique key; and a reporting engine incommunication with the database.
 2. The system of claim 1, wherein theunique key is 25 characters in length.
 3. The system of claim 1, whereinthe package quantity identifier is 3 characters in length.
 4. The systemof claim 1, wherein the data feed comprises national drug code data. 5.The system of claim 1, wherein the unique key comprises the therapeuticclass identifier, the clinical formulation identifier and the unit doseidentifier.
 6. A method for comparing drug product informationcomprising: parsing a data feed; assembling a unique key, wherein theunique key comprises a package quantity identifier and at least one of atherapeutic class identifier, a clinical formulation identifier, anadditional detail identifier, a package size equivalent identifier, anda unit dose identifier; storing the unique key in a database; receivingreport criteria; retrieving report data based on the report criteriausing the unique key; and outputting the report data to a user.
 7. Themethod of claim 6, wherein the unique key is 25 characters in length. 8.The method of claim 6, wherein the package quantity identifier is 3characters in length.
 9. The method of claim 6, wherein the unique keycomprises a package quantity identifier, a therapeutic identifier, aclinical formulation identifier, a unit dose identifier and at least oneof an additional detail identifier and a package size equivalentidentifier.
 10. The method of claim 9, wherein the unique key is 25characters in length.
 11. The method of claim 10, wherein the packagequantity identifier is 3 characters in length.
 12. The method of claim6, wherein the report data comprises national drug code data.
 13. Themethod of claim 6, wherein the report data is grouped according to thereport criteria.
 14. The method of claim 13, wherein the report data isfurther grouped according to bid price.